home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group02b.txt
/
000033_icon-group-sender_Tue Sep 17 08:25:54 2002.msg
< prev
next >
Wrap
Internet Message Format
|
2003-01-02
|
2KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.11.1/8.11.1) id g8HFOTU05746
for icon-group-addresses; Tue, 17 Sep 2002 08:24:29 -0700 (MST)
Message-Id: <200209171524.g8HFOTU05746@baskerville.CS.Arizona.EDU>
Date: Tue, 17 Sep 2002 10:36:37 +0200
From: TrolletAtskynetDOTbe <complaint@nospam.org>
X-Accept-Language: en
X-Newsgroups: comp.lang.icon
Subject: Re: Icon Wish 2
X-Complaints-To: abuse@skynet.be
To: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Christopher Browne wrote:
> There seem to be two other implementations of the ".NET VM," which
> /could/ be a counterargument. But I doubt they will be /realistic/
> alternatives to .NET anymore than the "UNIX port" of DCOM made it
> realistic to deploy COM-based applications on UNIX.
I put a :-) after my question 'What is .NET' - but I was serious when I
wrote it.
Let me think .. when did I first hear of it? Two years back?
When did I last hear of it? Two years back.
So it has become an integral part of Windows development after all?
As long as it doesn't infect non-Windows areas, I guess that is OK.
Everybody seemed to agree that a framework like .NET was a Good Thing
(tm) but they also suspected that Microsoft would certainly find a way
to take a Good Thing and do something bad with it ... so they did, it
seems.
Two years back, I wanted to find out what it was ... now I am more
relaxed about it.
> It would seem to me to make a /lot/ more sense to try to deploy Icon
> atop the upcoming Perl "Parrot" bytecode system. Consider that:
> a) It /is/ intended to be portable;
> b) There is intent for it to be not /totally/ Perl-oriented, as the
> Python and Ruby communities have had discussions about cooperation;
> c) It is not inconceivable that you could submit changes to Parrot to
> the Perl team, and have /some/ hope of them being accepted.
If Icon can find its way in between Perl and C somewhere ... I guess it
might benefit from taking advantage of a Perl source-to-bytecode
compiler/bytecode runtime in one end and icont in the other?
Of course, if a bytecode-to-binary compiler is made, then icont is not
needed ... and Perl becomes a compiled language, too.
Good idea?
Atle